Systems and methods for a location server to efficiently obtain location information from a location management entity

ABSTRACT

In one aspect there is provided a method performed by a first location management entity, LME (e.g., an MME or an SGSN), for providing location information to a location server (e.g., a GMLC). The method includes the first LME receiving from the location server a first request for location information pertaining to a terminal. The method also includes the first LME determining whether the terminal is in a connected state. The method further includes the first LME, in response to determining that the terminal is in a connected state, performing a method comprising: i) transmitting a stop paging message to a second LME; ii) obtaining the requested location information pertaining to the terminal; and iii) transmitting the obtained location information to the location server.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. application Ser. No.14/484,946, filed on Sep. 12, 2014 (published as U.S. 2105/0080022),which (1) claims the benefit of provisional patent application No.61/877,541 filed on Sep. 13, 2013 and (2) is a continuation ofinternational patent application no. PCT/EP20141068795, filed on Sep. 4,2014. The above-identified applications are incorporated by referenceherein.

TECHNICAL FIELD

The present invention relates to system and methods for a locationserver to efficiently obtain location information from a locationmanagement entity.

BACKGROUND

A location server, such as a Gateway Mobile Location Center (GMLC),functions to provide location information pertaining to a communicationdevice (a.k.a., “terminal” or “user equipment (UE)”) to a clientrequesting the information. Under the 3GPP standard (TS23.271 Functionalstage 2 description of Location Services (LCS)), the GMLC requestsrouting information from a Home Location Registry/Home Subscriber Server(HLR/HSS), which routing information is used by the GMLC to requestlocation information identifying the location of a terminal from alocation management entity, such as a Mobility Management Entity (MME)or a Serving Gateway Support Node (SGSN), that is handling the terminal.

If the terminal has been camping on both E-UTRAN and UTRAN/GERAN, thenthe HSS/HLR may respond to GMLC with routing information for both an MMEand an SGSN. This routing information does not contain any informationabout the RAT in which the terminal is located, nor does the routinginformation include information identifying the connection state the ofuser terminal (e.g., if the terminal is in connected or idle state).Accordingly, the GMLC will not know in which RAT the terminal is campingand, thus, it may send the location request to any of the SGSN or theMME, which may result in a Radio Access Network (RAN) (e.g., E-UTRAN)paging the terminal even though the terminal is already connected toanother RAN (e.g., UTRAN/GERAN), which is inefficient and wastesresources.

SUMMARY

This disclosure provides embodiments that reduce such inefficiencies.Advantages of the embodiments include: (1) reducing the amount ofsignaling between the GMLC and the SGSN/MME; (2) reducing unsuccessfulor wasteful terminal paging; and (3) increasing the response rate of theGMLC (e.g., the GMLC is able to obtain the requested locationinformation more quickly).

In particular, in one aspect there is provided a method performed by afirst location management entity, LME (e.g., an MME or an SGSN), forproviding location information to a location server (e.g., a (GMLC). Themethod includes the first LME receiving from the location server a firstrequest for location information pertaining to a terminal. The methodalso includes the first LME determining whether the terminal is in aconnected state. The method further includes the first LME, in responseto determining that the terminal is in a connected state, performing amethod comprising: i) transmitting a stop paging message to a secondLME; ii) obtaining the requested location information pertaining to theterminal; and iii) transmitting the obtained location information to thelocation server.

In some embodiments, the first LME is configured such that, in responseto determining that the terminal is not in a connected state, the firstLME: determines whether it has received a stop paging method from thesecond LME; and pages the terminal in response to determining that thefirst LME has not received a stop paging message from the second LME.

In some embodiments, the method also includes the first LME receivingfrom the location server a second request for location informationpertaining to a second terminal. As a result of receiving the secondrequest, the first LME pages the second terminal. The first LME thenreceives a stop paging message from the second LME and the first LMEceases paging of the second terminal in response to receiving the stoppaging message.

In some embodiments, the step of obtaining the requested locationinformation pertaining to the terminal comprises the first LMEtransmitting a message to a Serving Mobile Location Centre, SMLC, or anevolved SMLC, E-SMLC; and the first LME receiving a response messagefrom the SMLC or the E-SMLC, the response message comprising thelocation information pertaining to the terminal.

In another aspect a computer system is provided. The computer system isconfigured to determine whether a terminal is in a connected state inresponse to receiving from a location server a request for locationinformation pertaining to the terminal. The computer system is furtherconfigured, such that, in response to determining that the terminal isin a connected state, the computer system performs a method comprising:i) transmitting a stop paging message to a location management entity,LME; ii) obtaining the requested location information pertaining to theterminal; and iii) transmitting the obtained location information to thelocation server.

In another aspect there is provided a method performed by a firstlocation management entity, LME, for providing location information to alocation server, the first LME being connected to a first radio accessnetwork, RAN. The method includes the first LME receiving from thelocation server a request for location information pertaining to aterminal, The method also includes the first LME determining whether theterminal is in a connected state in the first RAN. The method furtherincludes the first LME, in response to determining that the terminal isnot in a connected state in the first RAN, performing a methodcomprising: transmitting a location request to a second LME connected toa second RAN; and receiving from the second LME a response messagecontaining state information identifying a state of the terminal in thesecond RAN.

In some embodiments, the method also includes: determining, based on thestate information, whether the terminal is in an idle state in thesecond RAN; and in response to determining that the terminal is in theidle state in the second RAN, paging the terminal.

In some embodiments, the method also includes determining whether theterminal is in a connected state in the first RAN after paging theterminal; and, in response to determining that the terminal is in theconnected state in the first RAN, sending a stop paging message to thesecond LME.

In some embodiments, the method also includes receiving a stop pagingmessage transmitted by the second LME after paging the terminal; andceasing paging the terminal in response to receiving the stop pagingmessage.

In another aspect, a computer system is provided, wherein the computersystem is configured to determine a connection state of a terminal in afirst radio access network, RAN, in response to receiving from alocation server a request for location information pertaining to theterminal. The computer system is further configured to perform aparticular method in response to determining that the connection stateof the terminal indicates that the terminal is not in a connected statein the first RAN. This method comprises: transmitting a location requestto a location management entity, LME; and receiving from the LME aresponse message containing information identifying a connection stateof the terminal in a second RAN.

The above and other aspects and embodiments are described below withreference to the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form partof the specification, illustrate various embodiments.

FIG. 1 illustrates a system according to some embodiments.

FIG. 2 is a flow chart illustrating a process according to someembodiments.

FIG. 3 is a flow chart illustrating a process according to someembodiments.

FIG. 4 is a flow chart illustrating a process according to someembodiments.

FIG. 5 is a message flow diagram, according to various embodiments, inthe case where the UE is in connected mode in the E-UTRAN/MME accesswhen the location requests are sent from the GMLC.

FIG. 6 is a message flow diagram, according to various embodiments, inthe case where the UE is in connected mode in the UTRAN/SGSN access whenthe location requests are sent from the GMLC.

FIG. 7 is a message flow diagram, according to various embodiments, inthe case where, when the location requests are sent from the GMLC, theUE is not in the connected mode in the UTRAN/SGSN access and also is notin the connected mode in the E-UTRAN/MME access (e.g., the UE is in idlemode)—as shown in FIG. 7, after being paged, the UE is in the connectedmode in the UTRAN/SGSN access.

FIG. 8 is a flow chart illustrating a process according to someembodiments.

FIG. 9 is a flow chart illustrating a process according to someembodiments.

FIG. 10 is a message flow diagram, according to some embodiments, forthe case where, when the single location request is sent from the GMLC,the UE is not in the connected mode in the UTRAN/SGSN access and also isnot in the connected mode in the E-UTRAN/MME access (e.g., the UE is inidle mode)—as shown in FIG. 10, after being paged, the UE is in theconnected mode in the E-UTRAN/MME access.

FIG. 11 is a block diagram of a computer according to some embodiments.

DETAILED DESCRIPTION

Referring now to FIG. 1, FIG. 1 illustrates a system 100 according tosome embodiments. System 100 is a wireless communication system thatenables a wireless communication device 102 to access a network 110,such as the Internet or other network. Communication device 102 is alsoreferred to as terminal 102. A location service (LCS) client 199 (e.g.,a third-party app) may desire to know the location of terminal 102.Accordingly, system 100 includes a location server 104, which, in theembodiment shown, is a GMLC 104.

As described in the background section above, when an entity requestsinformation identifying the location of terminal 102, the GMLC 104 maysend a location. request message to a location management entity (LME)that is responsible for managing terminal 102, which LME is connected toa RAN in which the terminal may be found (in the example system 100shown in FIG. 1, system 100 includes two LMEs: an MME 106 connected toRAN 121 (e.g., E-UTRAN) and a SGSN 108 connected to a RAN 122 (e.g.,UTRAN/GERAN)). The LME, in response to receiving the location requestmessage from the GMLC, may cause the RAN to start paging the terminal102 so that the terminal can transition from an idle state to aconnected state (e.g., so that a Radio Resource Control (RRC) connectionmay be established between terminal 102 and a network node (e.g., aneNodeB or an RNC)). As further described in the background section, suchpaging may be unnecessary when the terminal 102 is already connected toa RAN. Accordingly, described herein are steps performed by variousentities of system 100 that reduce the likelihood that an LME willunnecessarily page terminal 102.

Referring now to FIG. 2, FIG. 2 is a flow chart illustrating a process200 according to some embodiments. Process 200 may begin in step 201,where the MME 106 transmits a message 504 (e.g., an Update locationmessage) (see the message flow diagram shown in FIG. 5) to the HSS. Insome embodiments, the MME transmits message 504 as a result of receivingfrom RAN 121 (e.g., an eNodeB of RAN 121) an attach request messageindicating that terminal 102 has transmitted an attach request to RAN121. Additionally, the MME may transmit message 504 as a result ofreceiving from RAN 121 a tracking area update (TAU) request messageindicating that terminal 102 has transmitted such a message to RAN 121.The message 504 may contain at least one or more of: an address for aninterface of the MME (the address may be an IP address or a hostname (orother identifier) that can be used to look-up an IP address), the MME'sidentity (which, in some embodiments, may be used to look-up an IPaddress for the MME), information indicating that the MME supportssignaling of location information over the S3 interface (an interfacebetween MME and SGSN), and an identity of terminal 102 (e.g. MMEidentity). In some embodiments, the MME includes the address in message504 only if the MME's address for the S3 interface is different than theMME's address for the S6a/d interface.

In step 202, the SGSN 108 transmits a message 502 (e.g., an Updatelocation message) to the HSS. In some embodiments, the SGSN transmitsmessage 502 as a result of receiving from RAN 122 an attach requestmessage indicating that terminal 102 has transmitted an attach requestto RAN 122. Additionally, the SGSN may transmit message 502 as a resultof receiving from RAN 121 a routing area update (RAU). The message 502may contain at least one or more of: an address for an interface of theSGSN (the address may be an IP address or a hostname (or otheridentifier) that can be used to look-up an IP address), the SGSN'snumber (which, in some embodiments, may be used to look-up an IP addressfor the SGSN), information indicating that the SGSN supports signalingof location information over the S3 interface, and an identity ofterminal 102. In some embodiments, the SGSN includes the address inmessage 502 only if the SGSN's address for the S3 interface is differentthan the SGSN's address for the S6a/d interface.

In step 203, the SGSN stores state information identifying the currentconnection state of terminal 102 with respect to RAN 122. In step 204,the MME stores state information identifying the current connectionstate of terminal 102 with respect to RAN 121.

In step 205, the GMLC receives a location request message 506 (e.g., anLCS Service Request) from an LCS client (e.g., client 199), whichrequest message 506 requests location information pertaining to terminal102 (e.g. terminal 102's current location, terminal 102's velocity,and/or other location information). The request message 506, therefore,may include at the least an identity of terminal 102 or information fordetermining an identity of terminal 102 (e.g., information that enablesthe GMLC to determine the terminal 102's MSISDN or IMSI).

In step 206, in response to receiving location request message 506, theGMLC transmits a request message 508 (e.g., a Routing request message)to the HSS.

In step 208, the GMLC receives a response message 510 from HSS sent inresponse to the request message 508. In some embodiments, responsemessage 510 includes: an address for the SGSN (e.g., the addressincluded in message 502), an address for the MME (e.g., the addressincluded in message 504), information indicating that the SGSN supportssignaling of location information over the S3 interface, and informationindicating that the MME supports signaling of location information overthe S3 interface.

In step 212, as a result of receiving the response 510, the GMLC doesone or more of: (a) transmits a first location request 516 (e.g., afirst Subscriber Location Request message) to the MME and (b) transmitsa second location request 512 (e.g., a second Subscriber LocationRequest message) to the SGSN. The location requests 512/516 may containat least one or more of the following pieces of information: theidentity of terminal 102 (e.g., MSISDN, IMSI, IMEI, etc.); informationabout the LCS client 199 requesting the location of terminal 102;details about the location information being requested (e.g., currentlocation, velocity); QoS information (e.g. accuracy, response time).Additionally, message 512 may include information to enable the SGSN tocommunicate with the MME over the S3 interface (e.g., this informationmay include the MME's address included in message 510); and message 516may include information to enable the MME to communicate with the SGSNover the S3 interface (e.g., this information may include the SGSN'saddress included in message 510).

FIG. 3 is flow chart illustrating a process 300, according to someembodiments, performed by the MME when the GMLC transmits to the MME thelocation request 516 requesting location information pertaining toterminal 102. Process 300 may begin in step 302, where the MME receivesthe location request 516 from GMLC. In response, the MME determineswhether the terminal 102 is in a connected state. If the terminal 102 isin the connected state, then the process may proceed to steps 306-310,otherwise it may proceed to steps 312-318.

In step 306, the MME sends a stop paging message 517 to the SGSN.

In step 308, the MME obtains the requested location information forterminal 102. For example, in step 308, the MME may transmit to theEvolved Serving Mobile Location Centre (E-SMLC) 170 a request message518 requesting location information for terminal 102, and, in response,receive from the E-SMLC a response message 519 containing the requestedinformation (e.g., current location of the terminal, the velocity of theterminal, etc.).

In step 310, after obtaining the location information for terminal 102,the MME transmits to the GMLC a location response message 520 containingthe location information requested by the GMLC (e.g., containing atleast some of the location received from the SMLC).

In step 312, the MME determines whether it has received a stop pagingmessage 601 (see FIG. 6). If so, then it stops paging the terminal (ordoes not start paging the terminal) (step 316). Otherwise, the MME pagesthe terminal (step 314) (see FIG. 7, page 704, FIG. 10, page 704). Itstep 318, it determines whether the paging is successful (e.g., itdetermines whether the terminal is now connected to RAN 121—i.e., in aconnected state in RAN 121. if the paging is successful, then the MMEwould have received a page response 1099 (see FIG. 10) (e.g., a servicerequest message) and the process proceeds to steps 306-310, otherwise itproceeds back to step 312.

FIG. 4 is flow chart illustrating a process 400, according to someembodiments, performed by the SGSN when the GMLC transmits the locationrequest 512 to the SGSN. Process 400 may begin in step 402, where theSGSN receives the location request 512 from GMLC. In response, the SGSNdetermines whether the terminal 102 is in a connected state. If theterminal 102 is in the connected state, then the process may proceed tosteps 406-410, otherwise it may proceed to steps 412-418.

In step 406, the SGSN sends a stop paging message 601 to the MME.

In step 408, the SGSN obtains the requested location information forterminal 102. For example, in step 408, the SGSN may transmit to theServing Mobile Location Centre (SMLC) 171 a request message 602requesting location information for terminal 102, and, in response,receive from the SMLC a response message 603 containing the requestedinformation (e.g., current location of the terminal, the velocity of theterminal, etc.)

In step 410, after obtaining the location information for terminal 102,the SGSN transmits to the GMLC a location response message 604 (see FIG.6) containing the location information requested by the GMLC (e.g.,containing at least some of the location received from the SMLC).

In step 412, the SGSN determines whether it has received a stop pagingmessage 517. If so, then it stops paging the terminal (or does not startpaging the terminal) (step 416). Otherwise, the SGSN pages the terminal(step 414) (see FIG. 5, page 514). In step 418, it determines whetherthe paging is successful (e.g., it determines whether the terminal isnow connected to RAN 121). If the paging is successful, then the SGSNwould have received a page response 799 (see FIG. 7) (e.g., a servicerequest message) and the process proceeds to steps 406-310, otherwise itproceeds back to step 412.

After the GMLC receives message 520 or 604, each of which contains therequested location information, the GMLC may send to the requesting LCSclient a location response message 522 containing the locationinformation from message 520 or 604.

Referring now to FIG, 8, FIG. 8 illustrates a process 800 according toan alternative embodiment (an embodiment in which GMLC transmits alocation request to only one of the MME or SGSN, not both). Process 800may be performed by a location management entity (LME) (e.g., the MME orthe SGSN). For the sake of illustration, we shall assume that theprocess is performed by an SGSN (i.e., the GMLC has sent the request tothe SGSN, not the MME).

In step 802, the SGSN receives the location request message 512. In step804, the SGSN determines whether terminal 102 is connected to RAN 122.If so, then the process proceeds to step 808, otherwise it proceeds tostep 812.

In step 808, the SGSN obtains the requested location information forterminal 102 and then transmits to the GMLC the location response 604,

In step 812, the SGSN sends a location request 1002 (see FIG. 10) to theMME. In step 814 it receives from the MME a response 1004 to the requestmessage 1002. Using the information in the response 1004, the SGSNdetermines whether the terminal is connected to RAN 121. If it isconnected to RAN 121, then the SGSN need take no further action withrespect to the location request 512. If the terminal is not connected toRAN 121 (e.g., it is in an idle state), then process 800 proceeds tostep 818-826.

In step 818, the SGSN pages the terminal. In step 820, the SGSNdetermines whether it has received a stop paging message 517. If so,then it stops paging the terminal (step 822). Otherwise (step 824), theSGSN determines whether the paging is successful (e.g., it determineswhether the terminal is now connected to RAN 122). If the paging issuccessful, the process proceeds to steps 808-810 and the SGSN transmitsa message 601 to the MME.

FIG. 9 is a flow chart illustrating a process 900 performed by an LMEwhere the LME receives a location request from another LME, as opposedto receiving the location request directly from the GMLC. For the sakeof illustration and continuing with the example above, we shall assumethat process 900 is performed by the MME (i.e., the GMLC transmits alocation request to the SGSN, which then may transmit a location requestto the MME—see step 812).

Process 900 may begin in step 902, where the MME receives the locationrequest message 1002. In step 904 it transmit the response 1004 to theSGSN. The response message 1004 contains information identifying whetherthe terminal 102 is connected to RAN 121. If the terminal 102 isconnected to RAN 121, then the process proceeds to steps 908-910,otherwise it proceeds to steps 912-918. In step 908, the MME obtains therequested location information for terminal 102, and in step 910, theMME transmits the location response 520 to the GMLC. In step 912, theMME pages the terminal 102. In step 914 the MME determines whether ithas received a stop paging message 601. If so, then it stops paging theterminal (step 916). Otherwise (step 918), the MME determines whetherthe paging is successful (e.g., it determines whether the terminal isnow connected to RAN 121). If the paging is successful, the processproceeds to steps 920. In step 920, the MME sends the stop pagingmessage 517 to the SGSN to cause the SGSN to cease paging the terminal.After step 920, the process proceeds to steps 908-910, described above.

Each entity described herein (e.g., MME, SGSN, GMLC, etc.) may be asoftware entity that is executed by a computer system. FIG. 11 is ablock diagram of a computer system 1100 that may be used to execute oneor more of the entities described herein.

As shown in FIG. 11, computer system 1100 includes: a data processingsystem (DPS) 1102, which may include one or more processors (P) 1155(e.g., microprocessors) and/or one or more circuits, such as anapplication specific integrated circuit (ASIC), Field-programmable gatearrays (FPGAs), etc.; a network interface 1105 for receiving messagesfrom, and transmitting messages to, various nodes of network 110; a datastorage system 1106, which may include one or more computer-readabledata storage mediums, such as a non-transitory memory unit (e.g., harddrive, flash memory, optical disk, etc.) and/or volatile storageapparatuses (e.g., dynamic random access memory (DRAM)). In embodimentswhere data processing system 1102 includes a processor 1155 (e.g., amicroprocessor), a computer program product 1133 may be provided, whichcomputer program product includes: computer readable program code (CRPC)1143 (e.g., instructions), which implements a computer program, storedon a non-transitory computer readable medium 1142 of data storage system1106, such as, but not limited, to magnetic media (e.g., a hard disk),optical media (e.g., a DVD), memory devices (e.g., random accessmemory), etc. In some embodiments, computer readable program code 1143is configured such that, when executed by data processing system 1102,code 1143 causes the data processing system 1102 to perform stepsdescribed herein (e.g., steps shown in FIGS. 2-4, 8 and 9).

While various aspects and embodiments of the present disclosure havebeen described above, it should be understood that they have beenpresented by way of example only, and not limitation. Thus, the breadthand scope of the present disclosure should not be limited by any of theabove-described exemplary embodiments. Moreover, any combination of theelements described in this disclosure in all possible variations thereofis encompassed by the disclosure unless otherwise indicated herein orotherwise clearly contradicted by context,

Additionally, while the processes described herein and illustrated inthe drawings are shown as a sequence of steps, this was done solely forthe sake of illustration. Accordingly, it is contemplated that somesteps may be added, some steps may be omitted, the order of the stepsmay be re-arranged, and some steps may be performed in parallel.

The invention claimed is:
 1. A first location management entity (LME)apparatus, the LME apparatus comprising: a receiver; a transmitter, anda processing unit, comprising a processor, coupled to the transmitterand receiver, wherein the processing unit is configured such that, inresponse to the LME apparatus receiving from a location server a requestfor location information pertaining to a terminal, the processing unitdetermines whether the terminal is in a connected state in a first radioaccess network (RAN) to which the LME apparatus is connected, and theprocessing unit is further configured such that, in response todetermining that the terminal is not in a connected state in the firstRAN, the processing unit employs the transmitter to transmit to a secondLME apparatus connected to a second RAN a location request for causingthe second LME apparatus to transmit to the first LME apparatus aresponse message comprising state information identifying a state of theterminal in the second RAN.
 2. The LME apparatus of claim 1, wherein theprocessing unit is further configured to: determine, based on the stateinformation, whether the terminal is in an idle state in the second RAN;and page the terminal in response to determining that the terminal is inthe idle state in the second RAN.
 3. The LME apparatus of claim 2,wherein the processing unit is further configured to: determine whetherthe terminal is in a connected state in the first RAN after the terminalis paged; and employ the transmitter to transmit a stop paging messageto the second LME apparatus in response to determining that the terminalis in the connected state in the first RAN.
 4. The LME apparatus ofclaim 1, wherein the processing unit is further configured to ceasingpaging the terminal in response to receiving a stop paging messagetransmitted by the second LME apparatus.
 5. A method performed by afirst location management entity (LME) for providing locationinformation to a location server, the first LME being connected to afirst radio access network (RAN) the method comprising: the first LMEreceiving from the location server a request for location informationpertaining to a terminal; the first LME determining whether the terminalis in a connected state in the first RAN; and the first LME, in responseto determining that the terminal is not in a connected state in thefirst RAN, performing a method comprising: transmitting a locationrequest to a second LME connected to a second RAN; and receiving fromthe second LME a response message comprising state informationidentifying a state of the terminal in the second RAN.
 6. The method ofclaim 5, further comprising: determining, based on the stateinformation, whether the terminal is in an idle state in the second RAN;and in response to determining that the terminal is in the idle state inthe second RAN, paging the terminal.
 7. The method of claim 6, furthercomprising: after paging the terminal, determining whether the terminalis in a connected state in the first RAN; and in response to determiningthat the terminal is in the connected state in the first RAN, sending astop paging message to the second LME.
 8. The method of claim 6, furthercomprising: after paging the terminal, receiving a stop paging messagetransmitted by the second LME; and in response to receiving the stoppaging message, ceasing paging the terminal.
 9. A computer systemconfigured to: determine a connection state of a terminal in a firstradio access network (RAN) in response to receiving from a locationserver a request for location information pertaining to the terminal,wherein the computer system is further configured such that in responseto the computer system determining that the connection state of theterminal indicates that the terminal is not in a connected state in thefirst RAN, the computer system transmits a location request to alocation management entity (LME), and the computer system is operable toreceive from the LME a response message responsive to the locationrequest, wherein the response message comprises state informationidentifying a connection state of the terminal in a second RAN.
 10. Thecomputer system of claim 9, wherein the computer system is furtherconfigured to: determine, based on the received state information,whether the terminal is in an idle state in the second RAN; and inresponse to determining that the terminal is in the idle state in thesecond RAN, page the terminal.
 11. The computer system of claim 10,wherein the computer system is further configured to: after paging theterminal, determine whether the terminal is in a connected state in thefirst RAN; and in response to determining that the terminal is in theconnected state in the first RAN, send a stop paging message to the LME.12. The computer system of claim 10, wherein the computer system isfurther configured to: in response to receiving a stop paging messagetransmitted by the LME, cease paging the terminal.
 13. A computerprogram product comprising a non-transitory computer readable mediumstoring instructions to be performed by a first location managemententity (LME) apparatus, the instructions comprising: instructions fordetermining whether a terminal is in a connected state in a first radioaccess network (RAN) in response to the LME apparatus receiving from alocation server a request for location information pertaining to theterminal; instructions for employing a transmitter to transmit to asecond LME apparatus connected to a second RAN a location request forcausing the second LME apparatus to transmit to the first LME apparatusa response message comprising state information identifying a state ofthe terminal in the second RAN in response to determining that theterminal is not in a connected state in the first RAN; instructions fordetermining, based on the state information, whether the terminal is inan idle state in the second RAN; and instructions for paging theterminal in response to determining that the terminal is in the idlestate in the second RAN.